Computer data system position-index mapping

ABSTRACT

Described are methods, systems and computer readable media for position-index mapping in a computer data system.

This application claims the benefit of U.S. Provisional Application No. 62/161,813, entitled “Computer Data System” and filed on May 14, 2015, which is incorporated herein by reference in its entirety.

Embodiments relate generally to computer data systems, and more particularly, to methods, systems and computer readable media for position-index mapping.

Some conventional computer data systems may maintain data in one or more files that are indexed according to one or more key values. These conventional systems may store data in a relatively static form and that data may be copied to other tables or structures and indexed in those other tables as needed.

Some data systems may include data objects such as tables that include data from columns or other sources that may be referenced by other different tables or data objects. In such data systems, a need may exist to provide systems and methods for providing and maintaining a mapping between logical table indexes (or other data objects) and data positions within columns or other data sources.

Embodiments were conceived in light of the above mentioned needs, problems and/or limitations, among other things.

Some implementations can include a system comprising one or more hardware processors and a computer readable data storage device coupled to the one or more hardware processors, the computer readable data storage device having stored thereon software instructions that, when executed by the one or more hardware processors, cause the one or more hardware processors to perform operations. The operations can include receiving an electronic message associated with a child table, the electronic message including one or more change notifications indicating a change in one or more corresponding parent tables of the child table. The operations can also include updating an index of the child table based on the received one or more change notifications, where the index of the child table includes a mapping between one or more index values in the child table and corresponding positions in one or more data columns mapped by a columns source map of the child table, where the corresponding positions include positions for which data in the one or more data columns is valid for the child table.

The operations can further include, when the child table has one or more dependent tables that depend on data of the child table, generating one or more other electronic messages associated with the one or more dependent tables, the other electronic messages containing change notifications representing updates made to the child table. The operations can also include, when one or more other electronic messages are generated, providing the one or more other electronic messages to corresponding dependent tables.

The change notification can include one or more of an add, a modify, a delete or a reindex message associated with data in the child table that depends on data in one of the parent tables. The child table can include a dependency on data of the one or more parent tables.

The change notifications in the other electronic messages can include one or more of an add, a modify, a delete or a reindex message associated with data in the child table that depends on data in one of the parent tables. In some implementations, receiving the electronic message can include receiving an electronic message from a listener associated with the one or more parent tables. Providing the one or more other electronic messages to corresponding dependent tables can include causing a listener associated with the one or more dependent tables to be actuated. Some implementations can include another table having a same column source map as the child table and an index different from the index of the child table.

Some implementations can include a method comprising receiving an electronic message associated with a child table, the electronic message including one or more change notifications indicating a change in one or more corresponding parent tables of the child table. The method can also include updating an index of the child table based on the received one or more change notifications, where the index of the child table includes a mapping between one or more index values in the child table and corresponding positions in one or more data columns mapped by a columns source map of the child table, where the corresponding positions include positions for which data in the one or more data columns is valid for the child table.

The method can further include, when the child table has one or more dependent tables that depend on data of the child table, generating one or more other electronic messages associated with the one or more dependent tables, the other electronic messages containing change notifications representing updates made to the child table. The method can also include, when one or more other electronic messages are generated, providing the one or more other electronic messages to corresponding dependent tables.

The change notification can include one or more of an add, a modify, a delete or a reindex message associated with data in the child table that depends on data in one of the parent tables. The child table can include a dependency on data of the one or more parent tables.

The change notifications in the other electronic messages can include one or more of an add, a modify, a delete or a reindex message associated with data in the child table that depends on data in one of the parent tables. Receiving the electronic message can include receiving an electronic message from a listener associated with the one or more parent tables.

Providing the one or more other electronic messages to corresponding dependent tables can include causing a listener associated with the one or more dependent tables to be actuated. Some implementations can include another table having a same column source map as the child table and an index different from the index of the child table.

Some implementations can include a nontransitory computer readable medium having stored thereon software instructions that, when executed by one or more processors, cause the one or more processors to perform operations. The operations can include receiving an electronic message associated with a child table, the electronic message including one or more change notifications indicating a change in one or more corresponding parent tables of the child table. The operations can also include updating an index of the child table based on the received one or more change notifications, where the index of the child table includes a mapping between one or more index values in the child table and corresponding positions in one or more data columns mapped by a columns source map of the child table, where the corresponding positions include positions for which data in the one or more data columns is valid for the child table.

The operations can further include, when the child table has one or more dependent tables that depend on data of the child table, generating one or more other electronic messages associated with the one or more dependent tables, the other electronic messages containing change notifications representing updates made to the child table. The operations can also include, when one or more other electronic messages are generated, providing the one or more other electronic messages to corresponding dependent tables.

The change notification can include one or more of an add, a modify, a delete or a reindex message associated with data in the child table that depends on data in one of the parent tables. The child table can include a dependency on data of the one or more parent tables.

The change notifications in the other electronic messages can include one or more of an add, a modify, a delete or a reindex message associated with data in the child table that depends on data in one of the parent tables. Receiving the electronic message can include receiving an electronic message from a listener associated with the one or more parent tables. Some implementations can include another table having a same column source map as the child table and an index different from the index of the child table. Some implementations can include another table having a same index as the child table and a column source map different from the column source map of the child table.

In any of the above-mentioned implementations, updating the index can include maintaining strict ordering of the index. Also, any of the above-mentioned implementations can include maintaining a redirection index mapping an outer index to an inner index.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of an example computer data system showing an example data distribution configuration in accordance with some implementations.

FIG. 2 is a diagram of an example computer data system showing an example administration/process control arrangement in accordance with some implementations.

FIG. 3 is a diagram of an example computing device configured for position-index mapping in accordance with some implementations.

FIG. 4 is a diagram of an example data system table structure showing an index and a column source map in accordance with some implementations.

FIG. 5 is a diagram of an example data system table structure showing a plurality of indexes and column source maps in accordance with some implementations.

FIG. 6 is a diagram of an example index tree structure in accordance with some implementations.

FIG. 7 is a flowchart of an example position-index mapping process in accordance with some implementations.

FIG. 8 is a diagram of an example relationship between index values, column source logical positions, column source physical locations and index, and physical storage addresses in accordance with some implementations.

DETAILED DESCRIPTION

Reference may be made herein to the Java programming language, Java classes, Java bytecode and the Java Virtual Machine (JVM) for purposes of illustrating example implementations. It will be appreciated that implementations can include other programming languages (e.g., groovy, Scala, R, Go, etc.), other programming language structures as an alternative to or in addition to Java classes (e.g., other language classes, objects, data structures, program units, code portions, script portions, etc.), other types of bytecode, object code and/or executable code, and/or other virtual machines or hardware implemented machines configured to execute a data system query.

FIG. 1 is a diagram of an example computer data system and network 100 showing an example data distribution configuration in accordance with some implementations. In particular, the system 100 includes an application host 102, a periodic data import host 104, a query server host 106, a long-term file server 108, and a user data import host 110. While tables are used as an example data object in the description below, it will be appreciated that the data system described herein can also process other data objects such as mathematical objects (e.g., a singular value decomposition of values in a given range of one or more rows and columns of a table), TableMap objects, etc. A TableMap object provides the ability to lookup a Table by some key. This key represents a unique value (or unique tuple of values) from the columns aggregated on in a byExternal( ) statement execution, for example. A TableMap object can be the result of a byExternal( ) statement executed as part of a query. It will also be appreciated that the configurations shown in FIGS. 1 and 2 are for illustration purposes and in a given implementation each data pool (or data store) may be directly attached or may be managed by a file server.

The application host 102 can include one or more application processes 112, one or more log files 114 (e.g., sequential, row-oriented log files), one or more data log tailers 116 and a multicast key-value publisher 118. The periodic data import host 104 can include a local table data server, direct or remote connection to a periodic table data store 122 (e.g., a column-oriented table data store) and a data import server 120. The query server host 106 can include a multicast key-value subscriber 126, a performance table logger 128, local table data store 130 and one or more remote query processors (132, 134) each accessing one or more respective tables (136, 138). The long-term file server 108 can include a long-term data store 140. The user data import host 110 can include a remote user table server 142 and a user table data store 144. Row-oriented log files and column-oriented table data stores are discussed herein for illustration purposes and are not intended to be limiting. It will be appreciated that log files and/or data stores may be configured in other ways. In general, any data stores discussed herein could be configured in a manner suitable for a contemplated implementation.

In operation, the input data application process 112 can be configured to receive input data from a source (e.g., a securities trading data source), apply schema-specified, generated code to format the logged data as it's being prepared for output to the log file 114 and store the received data in the sequential, row-oriented log file 114 via an optional data logging process. In some implementations, the data logging process can include a daemon, or background process task, that is configured to log raw input data received from the application process 112 to the sequential, row-oriented log files on disk and/or a shared memory queue (e.g., for sending data to the multicast publisher 118). Logging raw input data to log files can additionally serve to provide a backup copy of data that can be used in the event that downstream processing of the input data is halted or interrupted or otherwise becomes unreliable.

A data log tailer 116 can be configured to access the sequential, row-oriented log file(s) 114 to retrieve input data logged by the data logging process. In some implementations, the data log tailer 116 can be configured to perform strict byte reading and transmission (e.g., to the data import server 120). The data import server 120 can be configured to store the input data into one or more corresponding data stores such as the periodic table data store 122 in a column-oriented configuration. The periodic table data store 122 can be used to store data that is being received within a time period (e.g., a minute, an hour, a day, etc.) and which may be later processed and stored in a data store of the long-term file server 108. For example, the periodic table data store 122 can include a plurality of data servers configured to store periodic securities trading data according to one or more characteristics of the data (e.g., a data value such as security symbol, the data source such as a given trading exchange, etc.).

The data import server 120 can be configured to receive and store data into the periodic table data store 122 in such a way as to provide a consistent data presentation to other parts of the system. Providing/ensuring consistent data in this context can include, for example, recording logged data to a disk or memory, ensuring rows presented externally are available for consistent reading (e.g., to help ensure that if the system has part of a record, the system has all of the record without any errors), and preserving the order of records from a given data source. If data is presented to clients, such as a remote query processor (132, 134), then the data may be persisted in some fashion (e.g., written to disk).

The local table data server 124 can be configured to retrieve data stored in the periodic table data store 122 and provide the retrieved data to one or more remote query processors (132, 134) via an optional proxy.

The remote user table server (RUTS) 142 can include a centralized consistent data writer, as well as a data server that provides processors with consistent access to the data that it is responsible for managing. For example, users can provide input to the system by writing table data that is then consumed by query processors.

The remote query processors (132, 134) can use data from the data import server 120, local table data server 124 and/or from the long-term file server 108 to perform queries. The remote query processors (132, 134) can also receive data from the multicast key-value subscriber 126, which receives data from the multicast key-value publisher 118 in the application host 102. The performance table logger 128 can log performance information about each remote query processor and its respective queries into a local table data store 130. Further, the remote query processors can also read data from the RUTS, from local table data written by the performance logger, or from user table data read over NFS, for example.

It will be appreciated that the configuration shown in FIG. 1 is a typical example configuration that may be somewhat idealized for illustration purposes. An actual configuration may include one or more of each server and/or host type. The hosts/servers shown in FIG. 1 (e.g., 102-110, 120, 124 and 142) may each be separate or two or more servers may be combined into one or more combined server systems. Data stores can include local/remote, shared/isolated and/or redundant. Any table data may flow through optional proxies indicated by an asterisk on certain connections to the remote query processors. Also, it will be appreciated that the term “periodic” is being used for illustration purposes and can include, but is not limited to, data that has been received within a given time period (e.g., millisecond, second, minute, hour, day, week, month, year, etc.) and which has not yet been stored to a long-term data store (e.g., 140).

FIG. 2 is a diagram of an example computer data system 200 showing an example administration/process control arrangement in accordance with some implementations. The system 200 includes a production client host 202, a controller host 204, a GUI host or workstation 206, and query server hosts 208 and 210. It will be appreciated that there may be one or more of each of 202-210 in a given implementation.

The production client host 202 can include a batch query application 212 (e.g., a query that is executed from a command line interface or the like) and a real time query data consumer process 214 (e.g., an application that connects to and listens to tables created from the execution of a separate query). The batch query application 212 and the real time query data consumer 214 can connect to a remote query dispatcher 222 and one or more remote query processors (224, 226) within the query server host 1 208.

The controller host 204 can include a persistent query controller 216 configured to connect to a remote query dispatcher 232 and one or more remote query processors 228-230. In some implementations, the persistent query controller 216 can serve as the “primary client” for persistent queries and can request remote query processors from dispatchers, and send instructions to start persistent queries. For example, a user can submit a query to the persistent query controller 216, and the persistent query controller 216 starts and runs the query every day. In another example, a securities trading strategy could be a persistent query. The persistent query controller can start the trading strategy query every morning before the market opened, for instance. It will be appreciated that 216 can work on times other than days. In some implementations, the controller may require its own clients to request that queries be started, stopped, etc. This can be done manually, or by scheduled (e.g., cron jobs). Some implementations can include “advanced scheduling” (e.g., auto-start/stop/restart, time-based repeat, etc.) within the controller.

The GUI/host workstation can include a user console 218 and a user query application 220. The user console 218 can be configured to connect to the persistent query controller 216. The user query application 220 can be configured to connect to one or more remote query dispatchers (e.g., 232) and one or more remote query processors (228, 230).

FIG. 3 is a diagram of an example computing device 300 in accordance with at least one implementation. The computing device 300 includes one or more processors 302, operating system 304, computer readable medium 306 and network interface 308. The memory 306 can include position-index mapping application 310 and a data section 312 (e.g., for storing index data structures, column source maps, etc.).

In operation, the processor 302 may execute the application 310 stored in the memory 306. The application 310 can include software instructions that, when executed by the processor, cause the processor to perform operations for position-index mapping in accordance with the present disclosure (e.g., performing one or more of 702-706 described below).

The application program 310 can operate in conjunction with the data section 312 and the operating system 304.

In general, a data object, such as a table, can include an index and a column source map. The index can include information mapping logical data object index values to corresponding valid data positions within the column source(s) that make up the data object. The column source map can include mapping information mapping column names to associated column sources. Data objects such as tables typically reference column source data in columns sources indicated by the column source map. For example, column source data could reference a large column split over many files in many locations on disk, or it could refer to a small, in-RAM array. Primary tables, (i.e., tables that are sources of data) can have the ability to create change notifications, which can include one or more of an add message, a modify message, a delete message, and a reindex message (AMDR message) when their underlying data changes. Non-primary tables may generate change notification messages (e.g., AMDR messages) in response to their inputs (primary or non-primary) changing.

A plurality of tables can point at a given column source. A given table may have no more claim to “ownership” of a commonly referenced column source than another table that also references that same commonly referenced column source. The “ownership” of the column source may be handled in some implementations via Java references and garbage collection.

FIG. 4 is a diagram of an example data system table structure 400 showing a table 402 having an index 404 and a column source map 406. The column source map 406 provides a mapping between column names of the table 402 and one or more column sources (408, 410). The index 404 provides a mapping between index values of the table 402 and corresponding valid data regions of the one or more column sources (408, 410). It will be appreciated that a column source may be assembled from data in multiple physical locations (e.g., a first section from location 1 and second section from location 2, etc.).

FIG. 5 is a diagram of an example data system table structure 500 having a first table 502 and a second table 504. In this example, the two tables (502, 504) share a common column source map 506 and each table (502, 504) has a respective index (508, 510). Each index (508, 510) provides a mapping for its corresponding table index values and valid data regions in one or more column sources (512, 514). The indexes (508, 510) may be the same or different depending on the tables (e.g., 502, 504) that the indexes correspond to. If the tables are the same, then the indexes may be the same. If the tables are different, then the indexes may be different, even when the two tables use a common column source map. Further, if table 2 (504) is derived from table 1 (502), the table 2 valid data region(s) will be a subset of the table 1 valid data region region(s).

FIG. 6 is a diagram of an example index tree structure 600 having a first range 602 of valid data positions (or “k” values) corresponding to table index values (or “i” values) and a second range 604 of valid data positions. The tree structure 600 shown in FIG. 6 is an example of a possible implementation for an index. It will be appreciated that other data structures can be used to store the index. The index may be in ascending order, where the order of the index can define how the table should be iterated.

In some implementations, the address space for disk-backed tables (or other generally slower storage devices) can be a distinct concept from the tree structure used for index ranges in memory. Disk-backed tables can use ranges of indexes that can be thought of as being conceptually analogous to a multi-level page table used by virtual memory systems.

In some implementations, the index structure can include a list of non-negative 64-bit values. When two or more consecutive values are stored in the list, an optimization can be made that includes storing the beginning and end of the range. The end of the range is stored as the negation of the end. For example, an index of {0, 1, 2, 4, 6, 7} can be stored as {0, −2, 4, 6, −7}, which can reduce the memory footprint when an index has consecutive values, which may be common for many tables (e.g., the physical addressing described below).

As mentioned above, in some implementations the index is physically stored as a tree data structure. The index tree can include leaf nodes, which can contain a given number of “slots” (e.g., 64). Each node can contain a size and a count. The size can include the number of logical items, the count can include the number of filled slots. The slots are simply long values in the representation described above. Leaf nodes may be compressed or “packed” by storing an array of shorts or ints instead of longs with an offset/mask that is applied to the data items. This is useful, for example, when ranges of values within a single partition may be close together and storing those adjacent values as a short will reduce memory usage.

An interior node has pointers to a left and a right child, as well as the node's size, min, and max. This node configuration can permit traversal of the index to a particular position or key value efficiently.

Also, some implementations can provide for efficient index serialization when sending the indexes over the network or storing persistently. Each value can be stored as an offset from the last value (with negative numbers just a negated offset, to represent ranges). Further, the smallest data type required (e.g., bytes, shorts, ints or longs) can be used for the offsets, which can reduce the complexity/size of the index representation transmitted over a network. The example index of {0, 1, 2, 4, 6, 7} can be logically represented as {0, −2, 4, 6, −7}, and converted to offsets of {0, −2, 2, 2, −1}. With small numbers, the offsets/sizes may not provide as much benefit, however, when representing more complex address spaces, the offset/size optimizations can provide a more significant benefit.

FIG. 7 is a flowchart of an example position-index mapping process 700 in accordance with some implementations. Processing begins at 702, where a table (e.g., a child table such as 402, 502, 504 etc.) receives an electronic message containing one or more change notifications providing information about corresponding changes in one or more parent tables of the child table. Each change notification can include one or more of an add message, a modify message, a delete message, and a reindex message (or AMDR message). Each AMDR message can include one or more index values and, optionally, one or more data values. In addition to AMDR messages, column sources can provide data values from a previous clock cycle (e.g., an immediately preceding clock cycle from the start of the instant clock cycle) via a function provided by column source data objects configured to store and provide data value(s) from a previous clock cycle. The previous clock cycle data values can be useful for efficiently computing update operations incrementally. The change notifications may be received via one or more listeners associated with the child table and a corresponding parent table. Processing continues to 704.

At 704, the child table index and calculated columns are updated based on the received change notifications to reflect changes in one or more parent tables that are relevant to data of those tables for which the child table has a dependency. Processing continues to 706.

At 706, the child table sends electronic change notifications (e.g., AMDR messages) to any dependent tables (i.e., child tables of the child table) to reflect the changes made to the child table that may be relevant to any dependent tables. The change notifications may be provided to dependent tables via actuation of a listener for a respective dependent table.

It will be appreciated that 702-706 may be repeated. For example, 702-706 may be repeated during each update cycle of a logical system clock in which one or more change notification messages for the child table are available.

FIG. 8 is a diagram of an example relationship 800 between index values 802, column source logical positions 804, column source physical locations and indexes 806, and physical storage addresses 808.

It will be appreciated that each of the stages shown in FIG. 8 can represent an address translation. For example, the index 802 provides a list of valid addresses, and a translation from a position, to those valid addresses.

A column source may be unaware of row positions, but may be aware of the logical address space of that column source. For example, in an ArrayBackedColumnSource, the address space could be a simple range from 0 . . . n−1 that matches the backing array.

Disk backed column sources typically may be divided into regions, with each region representing an internal data partition. For example, the column source could identify a partition (e.g., a set of column files) using the high-order bits of the logical address, and a row within that partition using the low-order bits of the logical address.

As these addresses may need translation, some implementations can include a RedirectedColumnSource, which can include an inner address space (e.g., matching some other wrapped column source) and an outer address space (e.g., matching the address space for the index that is referencing it). Two examples of RedirectedColumnSources include, but are not limited to: (1) the result table from a sort( ) operation, and (2) when performing an update( ) operation, the result table reuses the original column sources and index, but creates an ArrayBackedColumnSource to hold the results of the update operation, with a RedirectionIndex to map the potentially sparse address space of the outer index to the potentially denser address space of the inner index.

It will be appreciated that the modules, processes, systems, and sections described above can be implemented in hardware, hardware programmed by software, software instructions stored on a nontransitory computer readable medium or a combination of the above. A system as described above, for example, can include a processor configured to execute a sequence of programmed instructions stored on a nontransitory computer readable medium. For example, the processor can include, but not be limited to, a personal computer or workstation or other such computing system that includes a processor, microprocessor, microcontroller device, or is comprised of control logic including integrated circuits such as, for example, an Application Specific Integrated Circuit (ASIC), a field programmable gate array (FPGA), a graphics processing unit (e.g., GPGPU or GPU) or the like. The instructions can be compiled from source code instructions provided in accordance with a programming language such as Java, C, C++, C #.net, assembly or the like. The instructions can also comprise code and data objects provided in accordance with, for example, the Visual Basic™ language, a specialized database query language, or another structured or object-oriented programming language. The sequence of programmed instructions, or programmable logic device configuration software, and data associated therewith can be stored in a nontransitory computer-readable medium such as a computer memory or storage device which may be any suitable memory apparatus, such as, but not limited to ROM, PROM, EEPROM, RAM, flash memory, disk drive and the like. The processor and/or computer readable medium can include photonics, spintronics, and/or quantum devices.

Furthermore, the modules, processes systems, and sections can be implemented as a single processor or as a distributed processor. Further, it should be appreciated that the steps mentioned above may be performed on a single or distributed processor (single and/or multi-core, or cloud computing system). Also, the processes, system components, modules, and sub-modules described in the various figures of and for embodiments above may be distributed across multiple computers or systems or may be co-located in a single processor or system. Example structural embodiment alternatives suitable for implementing the modules, sections, systems, means, or processes described herein are provided below.

The modules, processors or systems described above can be implemented as a programmed general purpose computer, an electronic device programmed with microcode, a hard-wired analog logic circuit, software stored on a computer-readable medium or signal, an optical computing device, a networked system of electronic and/or optical devices, a special purpose computing device, an integrated circuit device, a semiconductor chip, and/or a software module or object stored on a computer-readable medium or signal, for example.

Embodiments of the method and system (or their sub-components or modules), may be implemented on a general-purpose computer, a special-purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit element, an ASIC or other integrated circuit, a digital signal processor, a hardwired electronic or logic circuit such as a discrete element circuit, a programmed logic circuit such as a PLD, PLA, FPGA, PAL, GP, GPU, or the like. In general, any processor capable of implementing the functions or steps described herein can be used to implement embodiments of the method, system, or a computer program product (software program stored on a nontransitory computer readable medium).

Furthermore, embodiments of the disclosed method, system, and computer program product (or software instructions stored on a nontransitory computer readable medium) may be readily implemented, fully or partially, in software using, for example, object or object-oriented software development environments that provide portable source code that can be used on a variety of computer platforms. Alternatively, embodiments of the disclosed method, system, and computer program product can be implemented partially or fully in hardware using, for example, standard logic circuits or a VLSI design. Other hardware or software can be used to implement embodiments depending on the speed and/or efficiency requirements of the systems, the particular function, and/or particular software or hardware system, microprocessor, or microcomputer being utilized. Embodiments of the method, system, and computer program product can be implemented in hardware and/or software using any known or later developed systems or structures, devices and/or software by those of ordinary skill in the applicable art from the function description provided herein and with a general basic knowledge of the software engineering and computer networking arts.

Moreover, embodiments of the disclosed method, system, and computer readable media (or computer program product) can be implemented in software executed on a programmed general purpose computer, a special purpose computer, a microprocessor, or the like.

It is, therefore, apparent that there is provided, in accordance with the various embodiments disclosed herein, methods, systems and computer readable media for position-index mapping.

application Ser. No. 15/154,974, entitled “DATA PARTITIONING AND ORDERING” and filed in the United States Patent and Trademark Office on May 14, 2016, is hereby incorporated by reference herein in its entirety as if fully set forth herein.

application Ser. No. 15/154,975, entitled “COMPUTER DATA SYSTEM DATA SOURCE REFRESHING USING AN UPDATE PROPAGATION GRAPH” and filed in the United States Patent and Trademark Office on May 14, 2016, is hereby incorporated by reference herein in its entirety as if fully set forth herein.

application No. Ser. No. 15/154,979, entitled “COMPUTER DATA SYSTEM POSITION-INDEX MAPPING” and filed in the United States Patent and Trademark Office on May 14, 2016, is hereby incorporated by reference herein in its entirety as if fully set forth herein.

application No. Ser. No. 15/154,980, entitled “SYSTEM PERFORMANCE LOGGING OF COMPLEX REMOTE QUERY PROCESSOR QUERY OPERATIONS” and filed in the United States Patent and Trademark Office on May 14, 2016, is hereby incorporated by reference herein in its entirety as if fully set forth herein.

application No. Ser. No. 15/154,983, entitled “DISTRIBUTED AND OPTIMIZED GARBAGE COLLECTION OF REMOTE AND EXPORTED TABLE HANDLE LINKS TO UPDATE PROPAGATION GRAPH NODES” and filed in the United States Patent and Trademark Office on May 14, 2016, is hereby incorporated by reference herein in its entirety as if fully set forth herein.

application No. Ser. No. 15/154,984, entitled “COMPUTER DATA SYSTEM CURRENT ROW POSITION QUERY LANGUAGE CONSTRUCT AND ARRAY PROCESSING QUERY LANGUAGE CONSTRUCTS” and filed in the United States Patent and Trademark Office on May 14, 2016, is hereby incorporated by reference herein in its entirety as if fully set forth herein.

application No. Ser. No. 15/154,985, entitled “PARSING AND COMPILING DATA SYSTEM QUERIES” and filed in the United States Patent and Trademark Office on May 14, 2016, is hereby incorporated by reference herein in its entirety as if fully set forth herein.

application No. Ser. No. 15/154,987, entitled “DYNAMIC FILTER PROCESSING” and filed in the United States Patent and Trademark Office on May 14, 2016, is hereby incorporated by reference herein in its entirety as if fully set forth herein.

application No. Ser. No. 15/154,988, entitled “DYNAMIC JOIN PROCESSING USING REAL-TIME MERGED NOTIFICATION LISTENER” and filed in the United States Patent and Trademark Office on May 14, 2016, is hereby incorporated by reference herein in its entirety as if fully set forth herein.

application No. Ser. No. 15/154,990, entitled “DYNAMIC TABLE INDEX MAPPING” and filed in the United States Patent and Trademark Office on May 14, 2016, is hereby incorporated by reference herein in its entirety as if fully set forth herein.

application No. Ser. No. 15/154,991, entitled “QUERY TASK PROCESSING BASED ON MEMORY ALLOCATION AND PERFORMANCE CRITERIA” and filed in the United States Patent and Trademark Office on May 14, 2016, is hereby incorporated by reference herein in its entirety as if fully set forth herein.

application No. Ser. No. 15/154,993, entitled “A MEMORY-EFFICIENT COMPUTER SYSTEM FOR DYNAMIC UPDATING OF JOIN PROCESSING” and filed in the United States Patent and Trademark Office on May 14, 2016, is hereby incorporated by reference herein in its entirety as if fully set forth herein.

application No. Ser. No. 15/154,995, entitled “QUERY DISPATCH AND EXECUTION ARCHITECTURE” and filed in the United States Patent and Trademark Office on May 14, 2016, is hereby incorporated by reference herein in its entirety as if fully set forth herein.

application No. Ser. No. 15/154,996, entitled “COMPUTER DATA DISTRIBUTION ARCHITECTURE” and filed in the United States Patent and Trademark Office on May 14, 2016, is hereby incorporated by reference herein in its entirety as if fully set forth herein.

application No. Ser. No. 15/154,997, entitled “DYNAMIC UPDATING OF QUERY RESULT DISPLAYS” and filed in the United States Patent and Trademark Office on May 14, 2016, is hereby incorporated by reference herein in its entirety as if fully set forth herein.

application No. Ser. No. 15/154,998, entitled “DYNAMIC CODE LOADING” and filed in the United States Patent and Trademark Office on May 14, 2016, is hereby incorporated by reference herein in its entirety as if fully set forth herein.

application No. Ser. No. 15/154,999, entitled “IMPORTATION, PRESENTATION, AND PERSISTENT STORAGE OF DATA” and filed in the United States Patent and Trademark Office on May 14, 2016, is hereby incorporated by reference herein in its entirety as if fully set forth herein.

application No. Ser. No. 15/155,001, entitled “COMPUTER DATA DISTRIBUTION ARCHITECTURE” and filed in the United States Patent and Trademark Office on May 14, 2016, is hereby incorporated by reference herein in its entirety as if fully set forth herein.

application No. Ser. No. 15/155,005, entitled “PERSISTENT QUERY DISPATCH AND EXECUTION ARCHITECTURE” and filed in the United States Patent and Trademark Office on May 14, 2016, is hereby incorporated by reference herein in its entirety as if fully set forth herein.

application No. Ser. No. 15/155,006, entitled “SINGLE INPUT GRAPHICAL USER INTERFACE CONTROL ELEMENT AND METHOD” and filed in the United States Patent and Trademark Office on May 14, 2016, is hereby incorporated by reference herein in its entirety as if fully set forth herein.

application No. Ser. No. 15/155,007, entitled “GRAPHICAL USER INTERFACE DISPLAY EFFECTS FOR A COMPUTER DISPLAY SCREEN” and filed in the United States Patent and Trademark Office on May 14, 2016, is hereby incorporated by reference herein in its entirety as if fully set forth herein.

application No. Ser. No. 15/155,009, entitled “COMPUTER ASSISTED COMPLETION OF HYPERLINK COMMAND SEGMENTS” and filed in the United States Patent and Trademark Office on May 14, 2016, is hereby incorporated by reference herein in its entirety as if fully set forth herein.

application No. Ser. No. 15/155,010, entitled “HISTORICAL DATA REPLAY UTILIZING A COMPUTER SYSTEM” and filed in the United States Patent and Trademark Office on May 14, 2016, is hereby incorporated by reference herein in its entirety as if fully set forth herein.

application No. Ser. No. 15/155,011, entitled “DATA STORE ACCESS PERMISSION SYSTEM WITH INTERLEAVED APPLICATION OF DEFERRED ACCESS CONTROL FILTERS” and filed in the United States Patent and Trademark Office on May 14, 2016, is hereby incorporated by reference herein in its entirety as if fully set forth herein.

application No. Ser. No. 15/155,012, entitled “REMOTE DATA OBJECT PUBLISHING/SUBSCRIBING SYSTEM HAVING A MULTICAST KEY-VALUE PROTOCOL” and filed in the United States Patent and Trademark Office on May 14, 2016, is hereby incorporated by reference herein in its entirety as if fully set forth herein.

While the disclosed subject matter has been described in conjunction with a number of embodiments, it is evident that many alternatives, modifications and variations would be, or are, apparent to those of ordinary skill in the applicable arts. Accordingly, Applicants intend to embrace all such alternatives, modifications, equivalents and variations that are within the spirit and scope of the disclosed subject matter. 

What is claimed is:
 1. A system comprising: one or more hardware processors; a computer readable data storage device coupled to the one or more hardware processors, the computer readable data storage device having stored thereon software instructions that, when executed by the one or more hardware processors, cause the one or more hardware processors to perform operations including: receiving an electronic message associated with a child table, the electronic message including one or more received change notifications and including at least one or more data values from a previous clock cycle; updating an index of the child table based on the one or more received change notifications, where the index of the child table includes a mapping between one or more index values in the child table and corresponding positions in one or more data columns mapped by a columns source map of the child table, where the corresponding positions include positions for which data in the one or more data columns is valid for the child table; when the child table has one or more dependent tables that depend on data of the child table, generating one or more other electronic messages associated with the one or more dependent tables, the one or more other electronic messages containing a child table change notification indicating an update made to the child table; and when one or more other electronic messages are generated, providing the one or more other electronic messages to the one or more dependent tables.
 2. The system of claim 1, wherein the updating of the index includes maintaining a pre-determined ordering of the index.
 3. The system of claim 1, wherein the child table has a dependency on data of one or more parent tables.
 4. The system of claim 1, further comprising another table having a same index as the child table and a second columns source map different from the columns source map of the child table.
 5. The system of claim 1, wherein receiving the electronic message includes receiving the electronic message from a listener associated with a table of one or more parent tables.
 6. The system of claim 1, wherein providing the one or more other electronic messages to corresponding dependent tables includes causing a listener associated with the one or more dependent tables to be actuated.
 7. The system of claim 1, further comprising another table having a same columns source map as the child table and a second index different from the index of the child table.
 8. A method comprising: receiving an electronic message associated with a child table, the electronic message including one or more change notifications indicating a change in one or more parent tables of the child table; updating an index of the child table based on the one or more change notifications, where the index of the child table includes a mapping between one or more index values in the child table and corresponding positions in one or more data columns mapped by a columns source map of the child table, where the corresponding positions include positions for which data in the one or more data columns is valid for the child table, and where the index of the child table is serialized; determining that the child table has one or more dependent tables that depend on data of the child table; after performing the updating, generating one or more other electronic messages associated with the one or more dependent tables, the one or more other electronic messages containing a child table change notification indicating an update made to the child table; and providing the one or more other electronic messages to the one or more dependent tables.
 9. The method of claim 8, wherein the one or more change notifications include one or more of an add, a modify, a delete or a reindex message associated with pre-determined data in the child table that depends on data in one of the parent tables.
 10. The method of claim 8, wherein the child table has a dependency on data of the one or more parent tables.
 11. The method of claim 8, further comprising maintaining a redirection index mapping an outer index to an inner index.
 12. The method of claim 8, wherein receiving the electronic message includes receiving the electronic message from a listener associated with a table of the one or more parent tables.
 13. The method of claim 8, wherein providing the one or more other electronic messages to the one or more dependent tables includes causing a listener associated with a table of the one or more dependent tables to be actuated.
 14. The method of claim 8, wherein another table has a same columns source map as the child table and a second index different from the index of the child table.
 15. A method comprising: receiving an electronic message associated with a child table, the electronic message including one or more change notifications including at least one or more data values from a previous clock cycle; updating an index of the child table based on the one or more change notifications, where the index of the child table includes a mapping between one or more index values in the child table and corresponding positions in one or more data columns mapped by a columns source map of the child table, where the corresponding positions include positions for which data in the one or more data columns is valid for the child tablet; when the child table has one or more dependent tables that depend on data of the child table, generating one or more other electronic messages associated with the one or more dependent tables, the one or more other electronic messages containing a child table change notification indicating an update made to the child table; and when one or more other electronic messages are generated, providing the one or more other electronic messages to the one or more dependent tables.
 16. The method of claim 15, further comprising: determining that a dependent table depends on data of the child table; and after performing the updating, providing a second electronic message to the dependent table, the second electronic message containing a child table change notification indicating an update made to the child table.
 17. The method of claim 15, wherein the one or more change notifications include one or more of an add, a modify, a delete or a reindex message associated with data in the child table that depends on data in a parent table.
 18. The method of claim 15, wherein the child table has a dependency on data of one or more parent tables.
 19. The method of claim 15, further comprising maintaining a redirection index mapping an outer index to an inner index.
 20. The method of claim 15, wherein receiving the electronic message includes receiving the electronic message from a listener associated with a table of one or more parent tables.
 21. The method of claim 16, wherein providing the second electronic message to the dependent table includes causing a listener associated with the dependent table to be actuated.
 22. The method of claim 15, wherein another table has a same columns source map as the child table and a second index different from the index of the child table.
 23. A nontransitory computer readable medium having stored thereon software instructions that, when executed by one or more processors, cause the one or more processors to perform operations including: receiving an electronic message associated with a child table, the electronic message including one or more change notifications indicating a change in one or more parent tables of the child table; updating an index of the child table based on the one or more change notifications, where the index of the child table includes a mapping between one or more index values in the child table and corresponding positions in one or more data columns mapped by a columns source map of the child table, where the corresponding positions include positions for which data in the one or more data columns is valid for the child table, and where the columns source map of the child table corresponds to a column source assembled from column data in multiple physical locations; when the child table has one or more dependent tables that depend on data of the child table, generating one or more other electronic messages associated with the one or more dependent tables, the one or more other electronic messages containing a child table change notification indicating an update made to the child table; and when one or more other electronic messages are generated, providing the one or more other electronic messages to the one or more dependent tables.
 24. The nontransitory computer readable medium of claim 23, the operations further including: determining that a dependent table depends on data of the child table; and after performing the updating, providing a second electronic message to the dependent table, the second electronic message containing a child table change notification indicating an update made to the child table.
 25. The nontransitory computer readable medium of claim 23, wherein the one or more change notifications include one or more of an add, a modify, a delete or a reindex message associated with data in the child table that depends on data in one of the parent tables.
 26. The nontransitory computer readable medium of claim 23, wherein the child table has a dependency on data of the one or more parent tables.
 27. The nontransitory computer readable medium of claim 24, wherein the notification in the second electronic message includes one or more of an add, a modify, a delete or a reindex message associated with pre-determined data in the child table.
 28. The nontransitory computer readable medium of claim 23, wherein receiving the electronic message includes receiving the electronic message from a listener associated with a table of the one or more parent tables.
 29. The nontransitory computer readable medium of claim 24, wherein providing the second electronic message to the dependent table includes causing a listener associated with the dependent table to be actuated.
 30. A system comprising: one or more hardware processors; a computer readable data storage device coupled to the one or more hardware processors, the computer readable data storage device having stored thereon software instructions that, when executed by the one or more hardware processors, cause the one or more hardware processors to perform operations including: receiving an electronic message associated with a child table, the electronic message including one or more change notifications indicating a change in one or more parent tables of the child table; updating an index of the child table based on the one or more change notifications, where the index of the child table includes a mapping between one or more index values in the child table and corresponding positions in one or more data columns mapped by a columns source map of the child table, where the corresponding positions include positions for which data in the one or more data columns is valid for the child table, and where the index of the child table is serialized; determining that the child table has one or more dependent tables that depend on data of the child table; and after performing the updating, generating one or more other electronic messages associated with the one or more dependent tables, the one or more other electronic messages containing a child table change notification indicating an update made to the child table.
 31. The system of claim 30, the operations further including: determining that a dependent table depends on data of the child table; and after performing the updating, providing a second electronic message to the dependent table, the second electronic message containing a child table change notification indicating an update made to the child table.
 32. The system of claim 30, wherein the updating the index includes maintaining a pre-determined ordering of the index.
 33. The system of claim 30, wherein the child table has a dependency on data of the one or more parent tables.
 34. The system of claim 30, further comprising another table having a same index as the child table and a second columns source map different from the columns source map of the child table.
 35. The system of claim 30, wherein receiving the electronic message includes receiving the electronic message from a listener associated with a table of the one or more parent tables.
 36. The system of claim 31, wherein providing the second electronic message to the dependent table includes causing a listener associated with the dependent table to be actuated.
 37. The system of claim 30, further comprising another table having a same columns source map as the child table and a second index different from the index of the child table. 